cfml

Screenshot 2023-10-03 at 10.43.35 AM.jpg

Howdy, is this bug already logged for Adobe Cf?

That is quirky, but why are you using a `writeoutput` inside a `cfoutput`?

And lucee does the smae thing, so I don't think it's a bug...  I think it's that `writeoutput` returns a boolean -- probably true if the value was successfully written or something...  but it's not documented.

Yeah - that's what is happening <https://cffiddle.org/app/file?filepath=bb92762b-7de9-4e5c-a5b8-b6c5e8e918b5/b93f8de7-7920-478d-9376-62408345fbba/b63bdc22-bd1a-4c3b-9429-7c7cbc3572fe.cfm>

<@U06UM62GN>, it was a hack to get around injecting into content that was wrapped in a big `<cfoutput encodefor="html">`…. which worked.. but got that bool

<@U035N9QFBA8> But why do you need the write output at all.  I assume, you're not using a boolean literal in your actual code, but a variable.  So just output the variable directly

```&lt;cfoutput encodefor="whatever"&gt;
  #myoutput#
&lt;/cfoutput&gt;```

Or, if you have your heart set on the `writeOPutput()` BIF specifically, then don't wrap it in hashes, call it from a cfset.
```&lt;cfoutput&gt;
  &lt;cfset writeOutput( myoutput ) &gt;
&lt;/cfoutput&gt;```
Now any return value from the function will be discarded, but it will still output to the page.

Thanks Brad, again we have an older piece of code that’s widely distributed I have to handle for.  (and I literally just don’t think in tags anymore, :slightly_smiling_face: )